Failed search on a shard tries a local replica on a network thread #4526
Labels
Comments
kimchy
added a commit
that referenced
this issue
Dec 19, 2013
When a search on a shard to a remove node fails, and then replica exists on the local node, then the execution of the search is done on the network thread. This is problematic since we need to execute it on the actual search thread pool, but can also explain #4519, where the get happens on the network thread and it waits to send the get request till the network thread we use is freed (deadlock...) fixes #4526 note, re-enable the geo shape fetch test, this fix should solve it as well
kimchy
added a commit
that referenced
this issue
Dec 19, 2013
When a search on a shard to a remove node fails, and then replica exists on the local node, then the execution of the search is done on the network thread. This is problematic since we need to execute it on the actual search thread pool, but can also explain #4519, where the get happens on the network thread and it waits to send the get request till the network thread we use is freed (deadlock...) fixes #4526 note, re-enable the geo shape fetch test, this fix should solve it as well
brusic
pushed a commit
to brusic/elasticsearch
that referenced
this issue
Jan 19, 2014
When a search on a shard to a remove node fails, and then replica exists on the local node, then the execution of the search is done on the network thread. This is problematic since we need to execute it on the actual search thread pool, but can also explain elastic#4519, where the get happens on the network thread and it waits to send the get request till the network thread we use is freed (deadlock...) fixes elastic#4526 note, re-enable the geo shape fetch test, this fix should solve it as well
mute
pushed a commit
to mute/elasticsearch
that referenced
this issue
Jul 29, 2015
When a search on a shard to a remove node fails, and then replica exists on the local node, then the execution of the search is done on the network thread. This is problematic since we need to execute it on the actual search thread pool, but can also explain elastic#4519, where the get happens on the network thread and it waits to send the get request till the network thread we use is freed (deadlock...) fixes elastic#4526 note, re-enable the geo shape fetch test, this fix should solve it as well
mute
pushed a commit
to mute/elasticsearch
that referenced
this issue
Jul 29, 2015
When a search on a shard to a remove node fails, and then replica exists on the local node, then the execution of the search is done on the network thread. This is problematic since we need to execute it on the actual search thread pool, but can also explain elastic#4519, where the get happens on the network thread and it waits to send the get request till the network thread we use is freed (deadlock...) fixes elastic#4526 note, re-enable the geo shape fetch test, this fix should solve it as well
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When a search on a shard to a remove node fails, and then replica exists on the local node, then the execution of the search is done on the network thread. This is problematic since we need to execute it on the actual search thread pool, but can also explain #4519, where the get happens on the network thread and it waits to send the get request till the network thread we use is freed (deadlock...)
The text was updated successfully, but these errors were encountered: